Fix access local registry by localhost:4873 when running in a devcontainer #28239
Conversation
… in a remote container
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit be42dd8. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
|
So the solution is to listen to 0.0.0.0 instead of localhost. I honestly do not know what is the principal difference - because it's not happening with any other web app i ran in containers, but as we can see they do this too in their docker container: |
ThePlenkov
changed the title
|
We need to check unit tests. Seems like jest is waiting for localhost to start e2e |
|
alternative to using the option would be probably not using port at all. It is a good question - why verdaccio is ignoring listen parameter in the config, probably because of the directly given port. It will be easier also to determine in e2e where verdaccio is running - it could be consumed form the config. |
Current Behavior
If repo is opened in a devcontainer on the local machine, verdaccio is not reachable by localhost:4873
Expected Behavior
Running command like
pnpm local-registryshould start a local registry and this registry must be reachable via localhostRelated Issue(s)
Fixes #28238